Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

• The PR has a single goal that is clear from the PR title and/or description.
• All code changes represent a single set of modifications that logically belong together.
• No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

• The code can be understood easily.
• Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
• There are no redundancies that can be removed by simple modularization/refactoring.
• There are no leftover debug statements or commented code sections.
• The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

• New functions and types are documented with a docstring or top-level comment.
• Relevant publications are referenced in docstrings (see example for formatting).
• Inline comments are used to document longer or unusual code sections.
• Comments describe intent ("why?") and not just functionality ("what?").
• If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

• The PR passes all tests.
• New or modified lines of code are covered by tests.
• New or modified tests run in less then 10 seconds.

Performance

• There are no type instabilities or memory allocations in performance-critical parts.
• If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

• The correctness of the code was verified using appropriate tests.
• If new equations/methods are added, a convergence test has been run and the results
  are posted in the PR.

Created with ❤️ by the Trixi.jl community.

Very cool feature, looking forward to it 😊

Moved the cubed sphere constructor here, making use of the new very convenient constructor which sets up tree_node_coordinates.

Codecov Report

Attention: Patch coverage is 96.42857% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 96.09%. Comparing base (8a9fc7b) to head (3158c44).

@@            Coverage Diff             @@
##             main    #1900      +/-   ##
==========================================
- Coverage   96.09%   96.09%   -0.00%     
==========================================
  Files         453      453              
  Lines       36461    36481      +20     
==========================================
+ Hits        35036    35055      +19     
- Misses       1425     1426       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

The PR is feature complete but needs some testing, reviewing and polishing. Furthermore, this PR depends on the latest developments in t8code, namely t8code version 2... The release is not public yet as are the Julia bindings for that. Hence, this PR has to wait for the t8code release before being ready for merging.

@benegee Please test your elixirs and add them to the test harness.

I added the tests. But I will need to adapt the error figures once the CI jobs are running.

@sloede @ranocha Incorporated your suggestions. I kindly ask for a second round of review.

@ranocha would you like to take a look as well? otherwise, this can be merged

@sloede @ranocha The PR should be ready for merge. Thank you very much for your reviews!